Thanks for your contribution @zation. I think this will conflict with the tour component, which uses tooltip.

Tour seems ok, but this does break custom triggers:

http://take.ms/xIxUJ

Hi @jbrowning
This is because when we click into that input, we both trigger "click" and "focus" event to hide that tooltip. I've fix that problem by detect if the trigger element is the element to show the tooltip itself, if so it won't be hide. Please have a look at it, it works in our project now.
Thanks!

It feels like this should be optional behavior. Registering a wholesale click event on body for a tooltip is likely to have unintended consequences.

Usually a tooltip is just that: a tooltip that is shown on click or a mouse enter event. Seems like you have a special case where you have a tooltip that stays open indefinitely? Could you give me a better idea of your use case?

Hi @jbrowning

I've stuble upon the same problem. The tap on body to close is pretty nice for mobile platform.
The original foundation will automatically add 'tap to close' at the bottom of each popup in the
case it detect it's a mobile platform.

I was wondering if this is still something that could be considerate to be merged if it was clean
up and rebase. I was maybe looking to do my own version and maybe add an event to close
all popup! The idea would be to be able to close popup before a modal open!

I have a lot of idea and I wanted to know if that is something that the angular-foundation would
consider mergable!

Thanks a lot for the info
Xavier LaRue